Skip to content

Update spack-packages submodule from upstream spack-packages/develop (includes #2025)#2039

Open
climbfuji wants to merge 17 commits into
JCSDA:developfrom
climbfuji:feature/update-spack-from-develop_all
Open

Update spack-packages submodule from upstream spack-packages/develop (includes #2025)#2039
climbfuji wants to merge 17 commits into
JCSDA:developfrom
climbfuji:feature/update-spack-from-develop_all

Conversation

@climbfuji

@climbfuji climbfuji commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator

Description

Update spack and spack-packages submodules from upstream spack/spack-packages develop as of the beginning of June, 2026.

This requires

  • pinning a few Python packages to work with the older Python 3.11 stack that we currently have
  • changing the way the Intel oneAPI modules are loaded in the site config (load compiler modules for MPI, don't load modules for MKL)
  • update cylc versions for compatibility with current Python 3.11 stack

Dependencies

Issues addressed

Applications affected

Potentially all. This PR has been tested for the end-to-end NEPTUNE ecosystem so far. Testing and bug fixes for other applications will be made by the respective stakeholders in follow-up pull requests.

Systems affected

Potentially all. Changes are made here for Atlantis only. Other site config updates will be made by the respective site maintainers in follow-up pull requests.

Testing

  • CI: Note whether the automatic tests (GitHub actions tests that run automatically for every commit) pass or not
    • GitHub actions CI tests pass
    • GitHub actions CI tests do not pass (provide explanation)
    • GitHub actions CI tests skipped (provide explanation if necessary)
  • New tests added: List and describe any new tests added to GitHub actions
    • ...
  • Additional testing: Add information on any additional tests conducted
    • On NRL's Atlantis: run NEPTUNE ecosystem end-to-end tests (including cylc workflow), run NEPTUNE CI tests

Checklist

  • This PR addresses one issue/problem/enhancement or has a very good reason for not doing so.
  • These changes have been tested on the affected systems and applications. see note above, section "Systems affected"
  • All dependency PRs/issues have been resolved and this PR can be merged.
  • All necessary updates to the documentation (spack-stack wiki) will be made when this PR is merged

@climbfuji climbfuji self-assigned this Jun 8, 2026
@climbfuji climbfuji changed the title Update spack-packages submodule from upstream spack-packages/develop Update spack-packages submodule from upstream spack-packages/develop (includes #2025) Jun 8, 2026
@climbfuji climbfuji moved this from Todo to In Progress in spack-stack-2.2.x (2026 Q?) Jun 8, 2026
@climbfuji climbfuji marked this pull request as ready for review June 23, 2026 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

Use spack-packages develop as base for spack-stack-dev

2 participants